User authentication using connection information provided by a blockchain network

ABSTRACT

Apparatuses, methods, and systems are disclosed for user authentication using a connection information package provided by a blockchain network. One apparatus includes a processor and a transceiver that receives, from a first address on a blockchain network, a plurality of connection information packages and also receives, from a first function, a request to authenticate a user. The processor determines whether the first function is associated with one of the plurality of connection information packages. In response to the first function being associated with a valid one of the plurality of connection information package, the processor accepts the request to authenticate a user.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to using a connectioninformation package from a blockchain network to authenticate a user ina visited network via an authentication server in the home network.

BACKGROUND

The following abbreviations and acronyms are herewith defined, at leastsome of which are referred to within the following description.

Third Generation Partnership Project (“3GPP”), Authentication,Authorization & Accounting (“AAA”), Access and Mobility ManagementFunction (“AMF”), Carrier Aggregation (“CA”), Clear Channel Assessment(“CCA”), Control Channel Element (“CCE”), Channel State Information(“CSI”), Common Search Space (“CSS”), Downlink Control Information(“DCI”), Downlink (“DL”), Enhanced Clear Channel Assessment (“eCCA”),Enhanced Mobile Broadband (“eMBB”), Evolved Node B (“eNB”), EuropeanTelecommunications Standards Institute (“ETSI”), Frame Based Equipment(“FBE”), Frequency Division Duplex (“FDD”), Frequency Division MultipleAccess (“FDMA”), Hybrid Automatic Repeat Request (“HARQ”),Internet-of-Things (“IoT”), Key Performance Indicators (“KPI”), LicensedAssisted Access (“LAA”), Load Based Equipment (“LBE”),Listen-Before-Talk (“LBT”), Long Term Evolution (“LTE”), LTA Advanced(“LTE-A”), Medium Access Control (“MAC”), Multiple Access (“MA”),Modulation Coding Scheme (“MCS”), Machine Type Communication (“MTC”),Massive MTC (“mMTC”), Multiple Input Multiple Output (“MIMO”), MultipathTCP (“MPTCP”), Multi User Shared Access (“MUSA”), Narrowband (“NB”),Network Function (“NF”), Next Generation Node B (“gNB”), Policy Control& Charging (“PCC”), Policy Control Function (“PCF”), Quality of Service(“QoS”), Quadrature Phase Shift Keying (“QPSK”), Radio Resource Control(“RRC”), Receive (“RX”), Switching/Splitting Function (“SSF”),Scheduling Request (“SR”), Session Management Function (“SMF”), SystemInformation Block (“SIB”), Transport Block (“TB”), Transport Block Size(“TBS”), Transmission Control Protocol (“TCP”), Time-Division Duplex(“TDD”), Time Division Multiplex (“TDM”), Transmission and ReceptionPoint (“TRP”), Transmit (“TX”), Uplink Control Information (“UCI”), UserDatagram Protocol (“UDP”), User Entity/Equipment (Mobile Terminal)(“UE”), Uplink (“UL”), Universal Mobile Telecommunications System(“UMTS”), Ultra-reliability and Low-latency Communications (“URLLC”),and Worldwide Interoperability for Microwave Access (“WiMAX”).

When a user is roaming outside the coverage area of its home network,the user may select to access a visited mobile network for obtainingaccess to mobile services. In order to access the visited mobile networka so-called roaming agreement must exist between the visited mobilenetwork and the home mobile network. This roaming agreement may bedirect between the two networks or may be indirect via a roaming hub.The roaming agreement enables secure connections to be establishedbetween the two networks in order to authenticate roaming users,transfer charging records, etc. As an example, the roaming agreementenables an Authentication, Authorization & Accounting (“AAA”) functionin the visited network to establish a connection to an AAA function inthe home network and to have the mobile user authenticated by the homemobile network. Thus, without a roaming agreement between the visitedand the home mobile networks a roaming user cannot be authenticated bythe home network and be authorized to access the visited network.

BRIEF SUMMARY

Methods for using a connection information package from a blockchainnetwork to authenticate a user in a visited network via anauthentication server in the home network are disclosed. Apparatuses andsystems also perform the functions of the methods. In some embodiments,a method of a network function for user authentication using aconnection information package provided by a blockchain network includesreceiving a request to authenticate a user, the request containing ausername and a realm, and identifying a first address on a blockchainnetwork corresponding to the realm. The method includes sending amessage to the first address on the blockchain network, the messagecontaining a payment, and receiving a connection information packagefrom the first address on the blockchain network after the payment isconfirmed. The method also includes establishing a connection with anauthentication server in the realm using the connection informationpackage and authenticating the user via the authentication server in therealm.

Another method of a network apparatus for user authentication using aconnection information package provided by a blockchain network includesa home AAA function receiving, from a first address on a blockchainnetwork, a plurality of connection information packages. Here, eachconnection information package is created in response to a message sentto the first address in the blockchain network. Said method alsoincludes receiving, from a first function, a request to authenticate auser and determining whether the first function is associated with avalid one of the plurality of connection information packages. Inresponse to the first function being associated with one of theplurality of connection information package, the method includesaccepting, at the home AAA function, the request to authenticate a user.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for using a connection information packagefrom a blockchain network to authenticate a user in a visited networkvia an authentication server in the home network;

FIG. 2 is a block diagram illustrating a blockchain network for using aconnection information package from a blockchain network to authenticatea user in a visited network via an authentication server in the homenetwork;

FIG. 3 is a block diagram illustrating one embodiment of a networkprocedure for user authentication using a connection information packageprovided by a blockchain network; Changes in FIG. 3: Added label “SmartContract 162 in the Blockchain Network 160” and added step 322. BWP:thanks

FIG. 4 a schematic block diagram illustrating one embodiment of anetwork function apparatus for using a connection information packagefrom a blockchain network to authenticate a user in a visited networkvia an authentication server in the home network;

FIG. 5A is a block diagram illustrating another embodiment of a networkprocedure for user authentication using a connection information packageprovided by a blockchain network; Changed label to “Smart Contract 162in the Blockchain Network 160”

FIG. 5B is a continuation of the network procedure of FIG. 5A; Changedlabel to “Smart Contract 162 in the Blockchain Network 160”

FIG. 6 is a schematic flow chart diagram illustrating one embodiment ofa method for user authentication using a connection information packageprovided by a blockchain network; and

FIG. 7 is a schematic flow chart diagram illustrating another embodimentof a method for user authentication using a connection informationpackage provided by a blockchain network.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects.

For example, the disclosed embodiments may be implemented as a hardwarecircuit comprising custom very-large-scale integration (“VLSI”) circuitsor gate arrays, off-the-shelf semiconductors such as logic chips,transistors, or other discrete components. The disclosed embodiments mayalso be implemented in programmable hardware devices such as fieldprogrammable gate arrays, programmable array logic, programmable logicdevices, or the like. As another example, the disclosed embodiments mayinclude one or more physical or logical blocks of executable code whichmay, for instance, be organized as an object, procedure, or function.

Furthermore, embodiments may take the form of a program product embodiedin one or more computer readable storage devices storing machinereadable code, computer readable code, and/or program code, referredhereafter as code. The storage devices may be tangible, non-transitory,and/or non-transmission. The storage devices may not embody signals. Ina certain embodiment, the storage devices only employ signals foraccessing code.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random-access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. This code may be provided to a processor of ageneral-purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the schematic flowchartdiagrams and/or schematic block diagrams.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus, orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theschematic flowchart diagrams and/or schematic block diagram.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods, and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, segment, or portion of code, which includes one ormore executable instructions of the code for implementing the specifiedlogical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

The disclosed embodiments consider online payments made via a blockchainnetwork. Such payments can be nearly real-time (fast) and can trigger asequence of other events, such as the creation and the assignment ofconnection information packages. Advantageously, this makes it possiblefor a mobile user to access a visited network (e.g. a mobile network ora WLAN network) even when the visited network does not have a roamingagreement with the user's home network.

FIG. 1 depicts a wireless communication system 100 for using aconnection information package from a blockchain network to authenticatea user in a visited network via an authentication server in the homenetwork, according to embodiments of the disclosure. In one embodiment,the wireless communication system 100 includes at least one remote unit105, an access network 120 containing at least one base unit 110,wireless communication links 115, a visited network 130, a home network140 of a remote unit 105, and a blockchain network 160. Even though aspecific number of remote units 105, access networks 120, base units110, wireless communication links 115, visited networks 130, homenetworks 140, and blockchain networks 160 are depicted in FIG. 1, one ofskill in the art will recognize that any number of remote units 105,access networks 120, base units 110, wireless communication links 115,visited networks 130, home networks 140, and blockchain networks 160 maybe included in the wireless communication system 100. In anotherembodiment, the access network 120 contains one or more WLAN (e.g.,Wi-Fi™) access points.

In one implementation, the wireless communication system 100 iscompliant with the 5G system specified in the 3GPP specifications. Moregenerally, however, the wireless communication system 100 may implementsome other open or proprietary communication network, for example, LTEor WiMAX, among other networks. The present disclosure is not intendedto be limited to the implementation of any particular wirelesscommunication system architecture or protocol.

In one embodiment, the remote units 105 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), smart appliances (e.g.,appliances connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), or thelike. In some embodiments, the remote units 105 include wearabledevices, such as smart watches, fitness bands, optical head-mounteddisplays, or the like. Moreover, the remote units 105 may be referred toas subscriber units, mobiles, mobile stations, users, terminals, mobileterminals, fixed terminals, subscriber stations, UE, user terminals, adevice, or by other terminology used in the art. The remote units 105may communicate directly with one or more of the base units 110 viauplink (“UL”) and downlink (“DL”) communication signals. Furthermore,the UL and DL communication signals may be carried over the wirelesscommunication links 115.

The base units 110 may be distributed over a geographic region. Incertain embodiments, a base unit 110 may also be referred to as anaccess terminal, an access point, a base, a base station, a Node-B, aneNB, a gNB, a Home Node-B, a relay node, a device, or by any otherterminology used in the art. The base units 110 may serve a number ofremote units 105 within a serving area, for example, a cell or a cellsector via a wireless communication link 115. The base units 110 maycommunicate directly with one or more of the remote units 105 viacommunication signals.

Generally, the base units 110 transmit downlink (“DL”) communicationsignals to serve the remote units 105 in the time, frequency, and/orspatial domain. Furthermore, the DL communication signals may be carriedover the wireless communication links 115. The wireless communicationlinks 115 may be any suitable carrier in licensed or unlicensed radiospectrum. The wireless communication links 115 facilitate communicationbetween one or more of the remote units 105 and/or one or more of thebase units 110.

The base units 110 are generally part of a radio access network (“RAN”),such as the access network 120, that may include one or more controllerscommunicably coupled to one or more corresponding base units 110. Theseand other elements of the radio access network are not illustrated, butare well known generally by those having ordinary skill in the art. Thebase units 110 connect to a mobile core network (e.g., in the visitednetwork 130) via the access network 120.

In one embodiment, the mobile core network is a 5G core (“5GC”) or theevolved packet core (“EPC”), which may be coupled to a data network 150,like the Internet and private data networks, among other data networks.Each mobile core network belongs to a single public land mobile network(“PLMN”). The present disclosure is not intended to be limited to theimplementation of any particular wireless communication systemarchitecture or protocol.

The mobile core network includes several network functions (“NFs”),including control plane functions (such as the AAA Function 132) anduser plane functions. As understood in the art, a mobile core networkmay include such control plane functions as an Access and MobilityManagement Function (“AMF”), a Session Management Function (“SMF”), aPolicy Control Function (“PCF”), and the Authentication, Authorization,and Accounting (“AAA”) Function 132.

The home network 140 is a “home” of the remote unit 105 roaming in thevisited network 130. As such, the remote unit 105 is a subscriber of thehome network 140 and has an account with the home network 140. Asdepicted, each of the visited network 130 and the home network 140maintains an AAA Function 132, used to authenticate remote units 105seeking services in the mobile communication networks. The visitednetwork 130 communicates with the home network 140 via the data network150.

Typically, a roaming agreement is needed between the home network 140and the visited network 130 in order for the visited network to provideservices to the roaming remote unit 105. However, the wirelesscommunication system leverages the blockchain network 160 to allowaccess authorization of a remote unit 105 in the visited network 130without requiring a pre-established roaming agreement between thevisited network 130 and the home network 140 of the remote unit 105.

As depicted, the blockchain network 160 is a peer-to-peer network thatmaintains a secure shared ledger 166, which is a list of transactionsthat have occurred in the past. This list of transactions is organizedinto blocks linked together, thus the name “blockchain.” The blockchainnetwork 160 is composed of multiple (typically thousands) of blockchainnodes 164, every one of which maintains a copy of the shared ledger 166.Note that the blockchain network 160 contains a single ledger 166 sharedamong the nodes 164 of the blockchain network 160.

Some blockchains, as the blockchain network 160 depicted, support socalled “smart contracts.” A smart contract is small program that isstored as part of the shared ledger 166 in all nodes 164 of theblockchain network 160. Typically, a smart contract 162 executes whenprescribed conditions are met, e.g., when it receives some funds. Inresponse, the smart contract 162 can perform various actions, such asreturning information (here a connection information package) to thesender of the funds, invoke other smart contracts, etc. Note that thesmart contract 162 is essentially a distributed application: it existsin all blockchain nodes 164 and it is executed simultaneously in allblockchain nodes 164. One advantage of such distributed application isimproved security as it is almost impossible to hack a smart contract162 because a hacker would have to change the contents of the sharedledger 166 in the majority of blockchain nodes 164.

Deployment of a smart contract 162 is typically done by sending ablockchain transaction to an empty address in the blockchain network 160with the smart contract byte code as data. Note that the byte code isthe code created after compiling the source code of the smart contract.Here, the smart contract 162 provides a (e.g., temporary) roamingagreement between the visited network 130 and the home network 140.

Each of the visited network 130 and home network 140 interface with theblockchain network 160 via the AAA function 132. In certain embodiments,the AAA function includes an external blockchain application, as discussin greater detail below. The AAA function 132 in the visited network 130can establish communication with the corresponding AAA function 132 inthe home network 140 via the data network 150; however, the AAA function132 only accepts connections from AAA functions 132 holding a validconnection information package. For example, a connection informationpackage may include a validity parameter, such as an expirationdate/time or number of uses remaining. If the AAA function 132 receivesa connection request that uses an expired connection informationpackage, then the AAA function 132 rejects the request.

The AAA function 132 in the visited network 130 acquires a connectioninformation package by sending funds to a smart contract 162 in theblockchain network 160; the smart contract 162 issuing a connectioninformation package after confirming payment. The connection informationpackages paid for and received by the visited network 130 are stored ina connection information package storage 136. The connection informationpackages issued by the smart contract 162 of the home network 140 arealso stored in a connection information package storage 136. In someembodiments, the AAA function 132 deletes connection informationpackages from the storage 126 in response to the connection informationpackages expiring or otherwise becoming invalid. Also, the home network140 has subscription data 144 which contains the subscriptioninformation of all its subscribers, including information required toauthenticate these subscribers.

FIG. 2 depicts a network architecture 200 used for using a connectioninformation package from a blockchain network to authenticate a user ina visited network via an authentication server in the home network,according to embodiments of the disclosure. The network architecture 200may be a simplified embodiment of the wireless communication system 100.As depicted, the network architecture 200 includes a UE 205 that isroaming in the visited network 130, a home network 140, and a blockchainnetwork 160. Here, the UE 205 may be one embodiment of the remote unit105, discussed above.

As depicted, the visited network 130 includes a visited AAA function215. Here, the visited AAA function (“VAF”) 215 is one embodiment of theAAA function 132 discussed above. Additionally, the home network 140includes a home AAA function (“HAF”) 220. The HAF 220 is also oneembodiment of the AAA function 132. Note that a mobile communicationnetwork may have a single AAA function 132 that acts both as a VAF 215for a visiting UE and as a HAF 220 for a home UE. As such, the AAAfunction 132 may combine the elements in the VAF 215 and the HAF 220,described in detail below.

As shown in FIG. 2, the VAF 215 and the HAF 220 each contain blockchainapplication, here the Visited blockchain application (“VBA”) 225 and theHome blockchain application (“HBA”) 235, respectively. Both the VBA 225and the HBA 235 are deployed as “external” blockchain applications withrespect to the blockchain network 160. The HBA 235 interfaces with theblockchain network via the blockchain external API 245 and isresponsible to deploy the smart contract 162. Moreover, the HBA 235receives notifications from the smart contract 162 whenever funds aretransferred to the smart contract 162 and a connection informationpackage is issued. All the connection information packages issued by thesmart contract 162 are reported to the HBA 235, which then stores themin the connection information package storage 136.

The VBA 225 interfaces with the blockchain network 160 and isresponsible to transfer funds to the smart contract 162 whenever itneeds to connect to the HAF 220 and has no valid connection informationpackage to enable this connection. The VBA 225 may request multipleconnection information packages, each one from a different home network140. This may be required to enable the visited network 130 to supportroaming users from multiple different home networks 140. The connectioninformation packages received by the visited network are stored in theconnection information package storage 136. Note that an AAA function132 may differentiate between “visited” connection information packagesit has purchased when acting as a VAF 215 and “home” connectioninformation packages it has received from a smart contract 162 is hasdeployed in the blockchain network 160. In some embodiments, the AAAfunction 132 deletes connection information packages from the storage126 in response to the connection information packages expiring orotherwise becoming invalid.

The blockchain network 160 provides application programming interfaces(APIs) that can be used by applications to interact with the blockchain.As an example, an application may use an API call to trigger ablockchain transaction via the blockchain interface 250, e.g. totransfer some funds to an account, or to be notified when his/heraccount receives new funds. As depicted, applications using theblockchain interface 250 via appropriate APIs can be external to ablockchain node 164, such as the VBA 225 and HBA 235, or an internalapplication 255 located in a blockchain node 164. In some embodiments,the blockchain network 160 supports an external API 245 (e.g., aJSON-RPC API) for use by external applications and a separate internalAPI 260 (e.g., a JavaScript™ API) for use by the internal applications255.

Recall that the smart contract 162 is deployed in all nodes 164 in theblockchain network 160. It is also assumed that the home network 140(i.e. the home blockchain application 235) is configured to listen tothe events emitted by the smart contract 162. Each of these eventsincludes a connection information package issued by the smart contract162.

The VAF 215 includes an AAA Proxy 230 used to contact the AAA Server 240in the home network 140 in order to authenticate a UE 205 that attemptsto roam in the visited network 130. Here, the UE 205 sends an accessrequest 210 that includes a username and home realm of the UE 205(depicted here as “user@realm”). If the VAF 215 does not have a validconnection information package for the home network 140 corresponding tothe realm, then the VBA 225 will initiate a blockchain transaction withthe smart contract 162 deployed by the home network 140 corresponding tothe realm (e.g., in order to purchase a connection information package).Thereafter, the AAA proxy 230 will use the connection informationpackage to connect to the AAA server 240, in order to authenticate theUE 205.

FIG. 3 depicts a network procedure 300 for user authentication using aconnection information package provided by a blockchain network,according to embodiments of the disclosure. The network procedure 300involves the UE 205, an access network 120, the visited AAA function 215(residing in the visited network 130), the home AAA function 220(residing in the home network 140), and the smart contract 162 in theblockchain network 160. The network procedure 300 does not require aroaming agreement between the visited network 130 and the home network140. Here, the network procedure 300 illustrates how the roaming user(the UE 205) is able to access a visited network that does not have aroaming agreement with the user's home network.

The network procedure 300 begins as the UE 205 attempts to access thevisited network via the access network 120. Here, the UE 205 associateswith the access network 120 (e.g., a WLAN AP) at which point the accessnetwork 120 initiates an EAP-based authentication procedure (seesignaling 305 and 310). Here, the access network 120 requests theidentity (e.g., a Network Access Identifier, “NAI”) of the UE 205 andthe UE 205 provides a username and realm in response (refer to signaling310). The access network 120 then sends an AAA Request to the AAAfunction in the visited network, here the visited AAA function 215 (seesignaling 315).

When the visited network (e.g., the visited AAA function 215) receivesthe access request from the roaming user, the visited AAA function 215performs an online payment by using a blockchain network 160, alsoreferred to as a blockchain service platform. In a typical case, thevisited AAA function 215 transfers some digital currency to a certainsmart contract 162 that has been deployed by the home mobile network inthe blockchain, in order to purchase a connection information packagethat authorizes connection to the home AAA function 220 for a validityperiod (see block 320). Note here, that the validity period (or numberof times a connection information package can be used) may be tied tothe payment amount. Here, a larger payment results in a longer validityperiod (or larger number of times a connection information package canbe used), while a smaller payment results in a smaller validity period(or smaller number of times a connection information package can beused).

When the smart contract 162 in the blockchain network 160 confirms thepayment, the smart contract 162 issues a new connection informationpackage which is made available to both the visited AAA function 215,which made the payment, and to the home AAA function 220, which owns thesmart contract 162 that received the payment (see signaling 322). Thisconnection information package authorizes the visited AAA function 215to connect to the home AAA function 220 and to request theauthentication of the roaming UE 205.

Prior to issuing this connection information package, any attempt by thevisited AAA function 215 to connect to the home AAA function 220 isrejected. After issuance of the connection information package, thevisited AAA function 215 makes a connection to the home AAA function 220using the connection information package and forwards the AAA Request tothe home AAA function 220 (see signaling 325). The home AAA function 220accepts the connection upon confirming that the visited AAA function 215owns a valid connection information package (see block 330). However,the AAA function 220 rejects a connection request that uses an expiredor otherwise invalid connection information package.

With the network procedure 300, there is no need for a pre-establishedroaming agreement and for extensive network configuration. The networkprocedure 300 enables a type of “temporary roaming agreement” that isimplemented as a smart contract 162 in a blockchain network 160. Toenter into the temporary roaming agreement, the visited network 130(e.g., via the visited AAA function 215) makes a secure and fast onlinepayment and receives a connection information package that permits itaccess to an authentication server in the home network 140. Moreover,the authentication server in the home network 140 accepts connectionrequests only from entities that have paid to obtain a connectioninformation package.

FIG. 4 depicts one embodiment of an authentication apparatus 400 thatmay be used for using a connection information package from a blockchainnetwork to authenticate a user in a visited network via anauthentication server in the home network, according to embodiments ofthe disclosure. The authentication apparatus 400 may be one embodimentof the AAA function 132. Furthermore, the authentication apparatus 400may include a processor 405, a memory 410, an input device 415, adisplay 420, and a transceiver 425. In some embodiments, the inputdevice 415 and the display 420 are combined into a single device, suchas a touch screen. In certain embodiments, the authentication apparatus400 may not include any input device 415 and/or display 420.

As depicted, the transceiver 425 includes at least one transmitter 430and at least one receiver 435. Additionally, the transceiver 425 maysupport at least one network interface 440. Here, the network interface440 facilitates communication with one or more a network function suchas the PCF 148. Additionally, the at least one network interface 440 mayinclude an interface used for communications with an externalapplication server, such as the application server 155.

The processor 405, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 405 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 405 executes instructions stored in thememory 410 to perform the methods and routines described herein. Theprocessor 405 is communicatively coupled to the memory 410, the inputdevice 415, the display 420, and the transceiver 425.

In some embodiments, the authentication apparatus 400 operates as avisited AAA function 215 of a remote unit 105, such as the UE 205. Insuch embodiments, the transceiver 425 receives a request to authenticatea user (e.g., the remote unit 105 or UE 205). Here, the request containsa username and a realm (e.g., a home realm of the user), for example inthe form of a NAI. In response to the request, the processor 405identifies a first address on a blockchain network 160, the firstaddress corresponding to the realm, and sends (e.g., by controlling thetransceiver 425) a message to the first address on the blockchainnetwork 160. Here, the message contains a payment, such as a transfer ofa blockchain payment from an address on the blockchain network 160belonging to the authentication apparatus 400 (e.g., from a secondblockchain address) to the first address. This payment may be a transferof funds, currency, cryptocurrency, assets (e.g., digital assets), orthe like.

In various embodiments, the first address may point to a smart contract162 that performs a computing function in response to the message. Here,the smart contract 162 may be executable code stored in the sharedledger 166 of the blockchain network 160. The smart contract 162implements a contract between the sender (e.g., the authenticationapparatus 400) and the owner or operator of the realm associated withthe smart contract 162. Note that the smart contract 162 is visible toall users of the blockchain network 160. Recall that the blockchainnetwork 160 contains a single ledger shared among the nodes of theblockchain network 160.

The message containing the payment causes the blockchain network 160 toinsert the transaction into the blockchain's shared ledger 166 and togenerate a connection information package, e.g., in response toconfirming the payment. The connection information package is associatedwith both the first address (e.g., pointing to the smart contract 162)and with the realm. Additionally, a copy of the connection informationpackage is sent to both the authentication apparatus 400 (e.g., as aresponse to the message containing the payment) and to an authenticationserver in the realm associated with the first address. Theauthentication apparatus 400 uses the connection information package toestablish a connection with the authentication server (e.g., the AAAserver 240 the home realm of the user). Having established theconnection to the authentication server, the authentication apparatus400 authenticates the user (e.g., via the authentication server in therealm). As discussed above, the authentication server may be a part of aAAA function (e.g., the home AAA function 220) in the home network ofthe user (e.g., the UE 205).

In some embodiments, the processor 405 identifies the first address onthe blockchain network (e.g., the first blockchain address) by mappingthe realm to an address on the blockchain network using a preconfiguredtable. In other embodiments, the processor 405 identifies the firstblockchain address by sending a DNS request, the DNS request includingthe realm, and receiving a DNS response, the DNS response including thefirst address on the blockchain network. In further embodiments, theprocessor 405 first checks the preconfigured table for a mapping andsends the DNS request if the table does not include a mapping for therealm. Moreover, the processor 405 may update the preconfigured tableupon receiving the DNS response.

In some embodiments, the message sent to the first blockchain addresscontains input data, including a network address of the authenticationapparatus 400 (referred to as a first network address). Here, the firstnetwork address may be an internet protocol (“IP”) address of theauthentication apparatus 400 or a hostname of the authenticationapparatus 400. Moreover, in response to the message including the firstnetwork address, the blockchain network (e.g., the smart contract 162)associates the connection information package with the first networkaddress. For example, the first network address may be included in theconnection information package. Note that the connection informationpackage is also associated with the realm.

In certain embodiments, the input data sent in the message to the firstblockchain address includes a public key of the authentication apparatus400. Here, the public key allows for improved security using theconnection information packages, as discussed below with reference toFIG. 5B.

In one embodiment, the processor 405 establishes the connection to theauthentication server in the realm using the first network address(e.g., sends from the first network address. The authentication server,in turn, verifies that the connection request is received from the samenetwork address as included in the connection information package.Moreover, the connection information package may include contactinformation pertaining to the authentication server, such as an IPaddress of the authentication server, a hostname of the authenticationserver, a protocol to be used to contact the authentication server,and/or a port to be used to connect to the authentication server in therealm. In certain embodiments, establishing the connection with theauthentication server includes sending a request message to theauthentication server, the request message comprising a reference to theconnection information package and a message authentication codecomputed with a private key associated with the public key of theapparatus.

In some embodiments, the connection information package includes avalidity parameter. In such embodiments, the authentication serververifies that the connection information package is valid prior toaccepting a connection request from the authentication apparatus 400. Inone embodiment, the validity parameter is an expiration time and date.Here, the connection information package becomes invalid after theexpiration time and date. In another embodiment, the validity parameteris an indicator of a permitted number of authentication requests usingthe connection information package. Here, the connection informationpackage becomes invalid after being used the permitted number of times.In certain embodiments, the validity parameter may include both anexpiration time/date and a permitted number of authentication requests.In some embodiments, the validity period (or number of times aconnection information package can be used) may be tied to the paymentamount. Here, a larger payment results in a longer validity period (orlarger number of times a connection information package can be used),while a smaller payment results in a smaller validity period (or smallernumber of times a connection information package can be used).

In some embodiments, the authentication apparatus 400 operates as a homeAAA function 220 of a remote unit 105, such as the UE 205. In suchembodiments, the processor 405 receives (via the transceiver 425), fromthe first address in the blockchain network 160 (e.g., the addressbelonging to the smart contract 162), a plurality of connectioninformation packages. Here, each connection information package createdin response to a message sent to the first address in the blockchainnetwork 160, the message including a payment to the first address in theblockchain and a network address that is to be associated with (e.g.,inserted into) the connection information package.

Note that the first address in the blockchain network 160 is the addressbelonging to the smart contract 162 corresponding to the realm in whichthe authentication apparatus 400 resides. Here, the payment triggers thesmart contract 162 to generate and distribute a connection informationpackage. For example, the smart contract 162 may send the generatedconnection information package in response to the payment being insertedinto a shared ledger 166 of the blockchain network 160. Recall that theblockchain network 160 contains a single ledger shared among the nodesof the blockchain network 160.

Moreover, the processor 405 receives (via the transceiver 425) a requestto authenticate a user from a first function (e.g., an AAA function in avisited network). In response to the request to authenticate the user,the processor 405 first determines whether the first function isassociated with one of the plurality of connection information packages.In certain embodiments, the processor 405 further confirms that theassociated connection information package is (still) valid. Then, inresponse to the first function being associated with a valid one of theplurality of connection information packages, the processor 405 acceptsthe request to authenticate the user. As used here, accepting therequest to authenticate refers to the processor 405 determining toinitiate an authentication procedure (e.g., EAP-based authentication),as described in further detail below.

In some embodiments, each connection information package comprises anetwork address of a corresponding function permitted to use theconnection information package and a realm of the apparatus, referred toas a first network address. The first network address may be an IPaddress or a hostname of the corresponding function.

Moreover, the request to authenticate a user may be received from asecond network address (e.g., an IP address belonging the firstfunction). In such embodiments, the processor 405 determines whether thefirst function is associated with a connection information package bydetermining whether the second network address matches the networkaddress included in (or otherwise associated with) a particularconnection information package. Where the first network address is ahostname, the processor 405 may also resolve the hostname into a firstIP address and determine whether the IP address associated with theauthentication request (e.g., the second IP address) matches the firstIP address. Note that the processor 405 will reject the authenticationrequest if the first function is not associated with any validconnection information package.

In certain embodiments, each connection information package may includea validity parameter, such as an expiration date/time and/or a maximumnumber of uses. Here, the processor 405 checks the validity of theconnection information package when determining whether the firstfunction is associated with one of the stored connection informationpackages. In addition, each connection information package may furtherinclude a public encryption key of the corresponding function. Moreover,the processor 405 may track the number of times a connection informationpackage has been used and update the usage number for the associatedconnection information package after accepting the request toauthenticate a user. In various embodiments, the processor 405 deletesconnection information packages in response to the connectioninformation packages expiring or otherwise becoming invalid.

In some embodiments, the request to authenticate a user include apackage identifier and a message authentication code. Here, the messageauthentication code is computed based on the private key of firstfunction. The processor 405 retrieves the particular connectioninformation package indicated by the package identifier. From theindicated connection information package, the processor 405 obtains thepublic key of the function corresponding to the connection informationpackage. If the processor 405 is successfully able to decode the messageauthentication code using the retrieves public key, then the processor405 has confirmed the authenticity of the authentication request andverifies that the first function is associated with the connectioninformation package (e.g., is permitted to connect to the authenticationapparatus 400 using the connection information package).

The memory 410, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 410 includes volatile computerstorage media. For example, the memory 410 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 410 includes non-volatilecomputer storage media. For example, the memory 410 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 410 includes bothvolatile and non-volatile computer storage media. In some embodiments,the memory 410 stores data relating to using a connection informationpackage from a blockchain network to authenticate a user in a visitednetwork via an authentication server in the home network, for examplestoring network addresses, blockchain addresses, connection informationpackages, and the like. In certain embodiments, the memory 410 alsostores program code and related data, such as an operating system orother controller algorithms operating on the authentication apparatus400 and one or more software applications.

The input device 415, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 415 maybe integrated with the display 420, for example, as a touchscreen orsimilar touch-sensitive display. In some embodiments, the input device415 includes a touchscreen such that text may be input using a virtualkeyboard displayed on the touchscreen and/or by handwriting on thetouchscreen. In some embodiments, the input device 415 includes two ormore different devices, such as a keyboard and a touch panel.

The display 420, in one embodiment, may include any known electronicallycontrollable display or display device. The display 420 may be designedto output visual, audible, and/or haptic signals. In some embodiments,the display 420 includes an electronic display capable of outputtingvisual data to a user. For example, the display 420 may include, but isnot limited to, an LCD display, an LED display, an OLED display, aprojector, or similar display device capable of outputting images, text,or the like to a user. As another, non-limiting, example, the display420 may include a wearable display such as a smart watch, smart glasses,a heads-up display, or the like. Further, the display 420 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the display 420 includes one or more speakersfor producing sound. For example, the display 420 may produce an audiblealert or notification (e.g., a beep or chime). In some embodiments, thedisplay 420 includes one or more haptic devices for producingvibrations, motion, or other haptic feedback. In some embodiments, allor portions of the display 420 may be integrated with the input device415. For example, the input device 415 and display 420 may form atouchscreen or similar touch-sensitive display. In other embodiments,the display 420 may be located near the input device 415.

The transceiver 425 communicates with one or more network functions of amobile communication network. The transceiver 425 operates under thecontrol of the processor 405 to transmit messages, data, and othersignals and also to receive messages, data, and other signals. Forexample, the processor 405 may selectively activate the transceiver (orportions thereof) at particular times in order to send and receivemessages. The transceiver 425 may include one or more transmitters 430and one or more receivers 435. As discussed above, the transceiver 425may support one or more the network interface 440 for communicating withthe base unit 110.

FIGS. 5A-5B depict a network procedure 500 for user authentication usinga connection information package provided by a blockchain network,according to embodiments of the disclosure. The network procedure 500 isone embodiment the network procedure 300, described above. The networkprocedure 500 involves the UE 205, an access network 120, the visitedAAA function 215 (residing in the visited network 130, not shown here),the home AAA function 220 (residing in the home network 140, not shownhere), and the smart contract 162 in the blockchain network 160. In thenetwork procedure 500, the UE 205 uses an access network 120 associatedwith the visited network 130 (e.g., the UE 205 attempts to roam in thevisited network 130). Here, there is no roaming agreement between thevisited network 130 and the home network 140.

Note, that the network procedure 500 assumes that there is initially novalid connection information package for the visited AAA function 215 touse to contact the home AAA function 220. Moreover, the networkprocedure 500 also assumes that the home network 140 has created a smartcontract 162 on the blockchain network 160 before the network procedure500 begins. It is further assumed that the home AAA function 220 (e.g.,the home blockchain application 235) is configured to listen to theevents emitted by the smart contract 162, each event including aconnection information package.

At FIG. 5A, the network procedure 500 begins with the UE 205 selectingan access network 120 (e.g., a WLAN AP) and initiating association withthe selected access network 120 (see signaling 505). After association,the UE 205 and the access network 120 begin an authentication procedure.In the depicted embodiments, the UE 205 and access network 120 use anEAP-based authentication procedure; however, other authenticationprocedures may be used in other embodiments.

In the authentication procedure, the access network 120 requests theUE's identity and the UE 205 responds by providing its Network AddressIdentifier (NAI), which includes a realm name and a username (seesignaling 510). The depicted NAI is in the form “username@realm;”however, in other embodiments the NAI may use other syntax. The “realm”includes the domain name of the home network 140, which holds the validsubscription of the user (e.g., the UE 205) and can be used toauthenticate the user.

The access network 120 forwards the EAP response (containing the NAI ofthe UE 205) to the visited AAA function (“VAF”) 215 in an AAA Requestmessage (see signaling 515). Generally, when the VAF 215 received an AAARequest message for a roaming user, the VAF 215 forwards the AAA Requestto the home AAA function of the user's realm. In the network procedure500, however, the VAF 215 determines that it cannot contact the Home AAAFunction (“HAF”) 220 in the home network 140 of the UE 205 because theVAF 215 does not have valid credentials (e.g., a valid connectioninformation package) for the HAF 220. In one embodiment, the lack ofconnection information package for the realm included in the NAItriggers an internal signal to the visited blockchain application 225(not shown here) which requests (e.g., to purchase) a connectioninformation package for the UE's realm (e.g., for the HAF 220 in theUE's home network 140).

As discussed above, the connection information package serves as anauthorization to connect to the HAF 220, e.g., in order to forward theAAA request message. Moreover, the connection information package mayinclude contact information for the HAF 220, such as hostname (or IPaddress) protocol, port, etc., for contacting the HAF 220.

To acquire a valid connection information package, the VAF 215 firstmaps the realm in the NAI to an address in the blockchain network 160 (Cblock 520). This address points to a smart contract (e.g., the smartcontract 162) capable of providing a connection information package forthe home network 140. In various embodiments, the visited blockchainapplication 225 maps the realm to a blockchain address. The blockchainaddress of the smart contract 162 is typically a long pseudo-randomcharacter string, for example the string0x888666CA69E0f178DED6D75b5726Cee99A87D698.

In some embodiments, the VAF 215 uses a preconfigured mapping table toidentify the blockchain address from the realm. Here, the preconfiguredmapping table may contain a list of supported realms and a blockchainaddress for a smart contract associated with each realm. In otherembodiments, the VAF 215 maps the realm to a blotting address by sendinga DNS request to a DNS server. For example, if the preconfigured mappingtable lacks an entry for the realm included in the NIA of the UE 205,then the VAF 215 sends the DNS request to retrieve the blockchainaddress of the smart contract for the realm. Note that the DNS requestmay be a special DNS request used to resolve realms into smart contractaddresses (e.g., in the blockchain network 160).

After identifying the blockchain address of the smart contract 162associated with the realm, the VAF 215 (e.g., the visited blockchainapplication 225) makes a call to the blockchain network (e.g., using theappropriate blockchain API) to initiate a new blockchain transaction. Toinitiate the block train transaction, the VAF 215 makes a payment to thesmart contract address and provides input data, including the IP address(or hostname) of the VAF 215 (see signaling 525). In variousembodiments, the payment may be a transfer of funds, an assignment ofdigital assets (such as cryptocurrency tokens), and the like. Thistransaction may be digitally signed using a private encryption keybelonging to the VAF 215.

Like all blockchain transactions, nodes inside the blockchain network160 confirm that the receive transaction is valid and signed by anentity possessing the right private key. This new transaction goes tothe normal mining process and is committed to the blockchain, e.g., byinsertion into the shared ledger 166 (see block 530). Note that in thenetwork procedure 500 it is important that the mining process iscompleted in a short period; otherwise, the entire authentication of theUE 205 may be considerably delayed. Hence, the transaction preferablyinvolves a blockchain with a short mining period.

In various embodiments, the transaction between the VAF 215 in the smartcontract 162 in the blockchain network 160 may contain the followinginformation: a digital signature (e.g., TxHash), a time step, thenetwork address of the sender (e.g., the IP address or hostname of theVA and 215), an address of the recipient (e.g., the blockchain addressof the smart contract 162), a value/payment (e.g., transferred funds orcrypto currency tokens), and input data (including a function of thesmart contract 162 to invoke, and input data such as the network addressof the VAF 215, the public key of the VAF 215, and the like).

After sending the request for a new blockchain transaction, the visitedblockchain application 225 of the VAF 215 configures the underlyingblockchain network 160 to report events emitted by the smart contract162. Such events are important because they provide the means for thesmart contract 162 to return some information to the VAF 215. Note thatany blockchain node 164 in the blockchain network 160 can monitor eventsemitted by a smart contract 162.

After receiving the funds from the VAF 215, the smart contract 162programming is executed, thereby creating a new connection informationpackage (see block 535). This is performed by executing code inside thesmart contract 162, e.g., corresponding to the function invoked in themessage from the VAF 215. In various embodiments, the smart contract 162creates a connection information package which contains the followinginformation: a connection package identification, a network address ofthe authorized user (e.g., the VAF 215), a validity parameter, accesscredentials, and contact information for the HAF 220. Note that theconnection package identification may uniquely identify the connectioninformation package and is used for logging purposes. The networkaddress of the authorized user may be an IP address or hostname. Thevalidity parameter may be an expiration time/date. Alternatively, thevalidity parameter may be a “count number” indicating a maximum numberof times the connection information package may be used before expiring.The contact information may include a network address (IP address orhostname) a communication protocol, a port, or the like forcommunicating with the HAF 220. In certain embodiments, the connectioninformation package also contains the public key of the VAF 215 (e.g.,assuming the public key was included as input data).

After creating the connection information package, the smart contract162 emits an event which contains the created connection informationpackage (see signaling 540). As a result, both the VAF 215 and the HAF220 receive a copy of the created connection information package. Bothfunctions save the new connection information package in theirconnection information package storage (136 and 146). Note that theconnection information package may also be received by any otherblockchain app application that monitors the events emitted by the smartcontract 162. However, the connection information package can be usedonly by a visited AAA function that possesses the IP address or hostnameincluded in the connection information package. In various embodiments,additional security measures may be taken as discussed below.

Continue at FIG. 5B, after receiving the connection information package,the VAF 215 establishes a connection with a home AAA server (e.g., inthe HAF 220) using the connection information package (see block 545).For example, the visited blockchain application 225 may instruct the AAAProxy 230 to forward the AAA Request to the AAA Server 240. In someembodiments, the VAF 215 uses the “Contact” information in theconnection information package to identify and contact the HAF 220.Alternatively, if the connection information package does not containthe “Contact” information, then the VAF 215 may use a DNS query todiscover the AAA Server for the provided username@realm, for example byusing the DNS-Based NAPTR/SRV Peer Discovery, as specified in RFC 7585.In response to identifying the AAA server, the AAA Proxy 230 in the VAF215 makes the connection to the AAA Server 240 in the HAF 220.

After making the connection, the VAF 215 forwards the AAA request (e.g.,received in signaling 515) to the HAF 220 (see signaling 550). The VAF215 sends the AAA Request in order to trigger the authenticationprocedure needed to authenticate the UE 205. The HAF 220 then validatesthe AAA Request (e.g., using the AAA Server 240). In doing so, the HAF220 confirms that the AAA Request comes from an IP address for which avalid connection information package exists in its connectioninformation package storage 146. If the validation fails, then the AAAServer 240 rejects the AAA Request, e.g., it denies authenticating theUE 205. However, if the validation succeeds, then the AAA Server 240accepts the AAA Request and performs an authentication procedure withthe UE 205 (see block 560). Here, the authentication can be based on anyEAP method according to the procedures known in the art.

After the authentication procedure completes (either successfully ornot), both the VAF 215 and the HAF 220 update the “count number” intheir connection information packages, if the connection informationpackage includes a validity “count number” (see blocks 575). Aftersuccessful authentication, the UE 205 is connected to the access network120 (see block 580) and gains access to services in the visited network130. Note that the VAF 215 and HAF 220 may delete connection informationpackages that have expired or otherwise become invalid.

In the network procedure 500, the HAF 220 uses the IP address of the VAF215 as a key for validating an authentication request. Recall that theconnection information package contains a network address belonging tothe function permitted to use the connection information package. Insome embodiments, the HAF 220 resolves a hostname in the connectioninformation package into an IP address, in order to validate the AAArequest. However, in other embodiments other types of validation may besupported.

Note that the connection information package emitted by the smartcontract 162 needs to be readable by both the VAF 215 and the HAF 220.Accordingly, it is not possible to encrypt the connection informationpackage by using the public key of VAF 215, as this would render theconnection information package unreadable to all except the VAF 215. Incertain embodiments, the smart contract 162 emits an unencrypted (e.g.,plaintext) notification that is readable by all entities (e.g. the HAFand all VAFs) that monitor the smart contract notifications. In otherembodiments, the smart contract 162 emits a notification containing twocopies of the connection information package: a first copy encryptedwith the public key of the VAF 215 and a second copy encrypted with thepublic key of the HAF 220. Here, although all entities would receive thenotification, only the HAF 220 and the VAF 215 who made the paymentwould be able to read the info package.

In some embodiments, the AAA Request message sent to the HAF 220 (referto signaling 550) may include a package identifier that points to aspecific connection information package, as well as a messageauthentication code (“MAC”) that is computed based on the private key ofVAF 215. In such embodiments, the HAF 220 retrieves the public key ofthe VAF 215 from the referenced connection information package andconfirms the authenticity of the MAC by using this public key. Here, aMAC that is decodable using the public key in the connection informationpackage confirms that the MAC was computed by an entity having the rightprivate key (e.g., the VAF 215 whose payment generated the connectioninformation package).

When validating a AAA Request using the MAC, the message the VAF 215sends to the smart contract 162 (refer to signaling 525) must includealso the public key of the VAF 215. Moreover, the smart contract 162must copy this public key into the created connection informationpackage. From a security point of view, the MAC-based validationprocedure is considered more secure than the IP Address basedvalidation, because it makes sure that the AAA Request to the HAF 220really comes from the entity that paid to receive the connectioninformation package. However, implementing the MAC may require changesto the AAA protocol between the VAF 215 and the HAF 220. In contrast,validating the AAA request using only the IP Address does not requirechanges to the AAA protocol, but it may be less secure as it onlyconfirms that the AAA Request sent to the HAF 220 comes from an entityusing the same IP address as the one declared when making the paymentfor the connection information package (e.g., the network addressassociated with the connection information package).

FIG. 6 depicts a method 600 for using a connection information packagefrom a blockchain network to authenticate a user in a visited networkvia an authentication server in the home network, according toembodiments of the disclosure. In some embodiments, the method 600 isperformed by an apparatus, such as the AAA function 132, the visited AAAfunction 215, and/or the authentication apparatus 400. In certainembodiments, the method 600 may be performed by a processor executingprogram code, for example, a microcontroller, a microprocessor, a CPU, aGPU, an auxiliary processing unit, a FPGA, or the like.

The method 600 begins and receives 605, at the network function, arequest to authenticate a user, the request containing a username and arealm. For example, the username may identify a user account (orsubscriber account) and the realm identifies a location of the useraccount. Here, the realm (also referred to as a realm name) may identifythe home realm of the user.

The method 600 includes identifying 610 a first address on a blockchainnetwork (e.g., a first blockchain address) that corresponds to therealm. In some embodiments, identifying 610 the first address on ablockchain network includes mapping the realm to an address (e.g., ablockchain address) using a preconfigured table. In other embodiments,identifying 610 the first blockchain address includes sending a domainname system (“DNS”) request, the request including the realm, andreceiving a DNS response, the DNS response including the first addresson the blockchain network. In certain embodiments, identifying 610 thefirst blockchain address includes first checking the preconfigured tablefor an entry corresponding to the realm and sending the DNS request ifthe preconfigured table does not include an entry corresponding to therealm.

The method 600 includes sending 615 a message to the first address onthe blockchain network, the message containing a payment. In certainembodiments, the first address on a blockchain network points to a smartcontract on the blockchain network. As described herein, the smartcontract is executable code (e.g., a computer program) stored in ashared ledger of the blockchain network. When the message meets certainconditions (e.g., contains a payment and identifies the sender), thenthe smart contract issues a connection information package, as describedbelow. Note that the blockchain network contains a single ledger sharedamong the nodes of the blockchain network.

In some embodiments, the payment contained in the message is ablockchain payment from a second address on the blockchain network tothe first address on the blockchain network, the second blockchainaddress belonging to an operator of the network function. In certainembodiments, the message sent to the first address includes a publicencryption key of the network function. In certain embodiments, themessage sent to the first address also includes a first network addressthat belongs to the network function.

The method 600 includes receiving 620 a connection information packagefrom the first address on the blockchain network after the payment isconfirmed. In certain embodiments, receiving the connection informationpackage from the first address on the blockchain network after paymentconfirmation includes receiving the connection information package inresponse to the payment being inserted into a shared ledger of theblockchain network.

As described above, the message may include a network address (e.g.,first network address) belonging to the network function. Here, thefirst network address may be an IP address or a hostname of the networkfunction. When included in the message, the connection informationpackage may include a first network address (e.g., the IP address orhostname of the network function). The connection information packagemay further include a public key of the network function. Moreover, theconnection information package is then associated with both the realmand the first network address. For example, the connection informationpackage may become usable only by an entity using the first networkaddress.

In some embodiments, the connection information package includes contactinformation of the authentication server, thereby indicating how thenetwork function can contact the authentication server in the realm. Invarious embodiments, such contact information may include an IP addressof the authentication server, a hostname of the authentication server, aprotocol to be used to contact the authentication server, and/or a portto be used to connect to the authentication server.

In any of the above embodiments, the connection information package mayinclude a validity parameter indicating a condition invalidating theconnection information package. In one embodiment, the validityparameter includes an expiration time and date. In such an embodiment,the connection information package becomes invalid after the expirationtime and date. In another embodiment, the validity parameter includes anindicator of a permitted number of authentication requests using theconnection information package. In such an embodiment, the connectioninformation package becomes invalid after being used the permittednumber of times.

The method 600 includes establishing 625 a connection with anauthentication server in the realm using the connection informationpackage. Here, the connection with the authentication server in therealm is made using the first network address. In various embodiments,the authentication server only accepts a connection request made usingthe connection information package if the request is sent from a networkaddress associated with the connection information package (e.g., thefirst network address belonging to the network function). In certainembodiments, establishing 625 the connection with the authenticationserver in the realm using the connection information package comprisessending a request message to the authentication server, the requestmessage comprising a reference to the connection information package anda message authentication code computed with a private key associatedwith the public key of the network function.

The method 600 includes authenticating 630 the user via theauthentication server in the realm and the method 600 ends. In any ofthe above embodiments, the authentication server in the realm may be anauthentication, authorization, and accounting (“AAA”) function in a homenetwork of the user. Authenticating 630 the user may also includeproviding services to the user in response to successful authentication.

In some embodiments, each connection information package comprises afirst network address of a corresponding function permitted to use theconnection information package and a realm of the authenticationfunction. The first network address may be an IP address and a hostnameof the corresponding function. In certain embodiments, each connectioninformation package further comprises a public encryption key of thecorresponding function.

In some embodiments, at least one of the plurality of connectioninformation packages includes a validity parameter. In certainembodiments, at least one connection information package includes, asthe validity parameter, an expiration time and date of the correspondingconnection information package. Here, the corresponding connectioninformation package becoming invalid after the expiration time and date.In certain embodiments, at least one connection information packageincludes, as the validity parameter, an indicator of a permitted numberof authentication requests using the corresponding connectioninformation package. Here, the corresponding connection informationpackage becoming invalid after being used the permitted number of times.

FIG. 7 depicts a method 700 for user authentication using a connectioninformation package provided by a blockchain network, according toembodiments of the disclosure. In some embodiments, the method 700 isperformed by an apparatus, such as the AAA function 132, the home AAAfunction 220, and/or the authentication apparatus 400. In certainembodiments, the method 700 may be performed by a processor executingprogram code, for example, a microcontroller, a microprocessor, a CPU, aGPU, an auxiliary processing unit, a FPGA, or the like.

The method 700 begins with receiving 705, at an authentication functionand from a first address on a blockchain network (e.g., from a firstblockchain address), a plurality of connection information packages.Here, each connection information package is created, e.g., by theblockchain network, in response to a message being sent to the firstaddress in the blockchain network.

More specifically, the message triggers a transaction with a smartcontract in the blockchain network, the transaction being recorded inthe shared ledger of the blockchain network, and the smart contractsends a connection information package to the authentication function.Here, the first blockchain address points to a smart contract associatedwith a realm of the authentication function. The message may include thepayment and a first address of the sender, such as an IP address or ahostname. In certain embodiments, receiving 705 the plurality ofconnection information packages includes receiving a connectioninformation package in response to the payment being inserted into ashared ledger of the blockchain network. Note that the blockchainnetwork contains a single ledger shared among the nodes of theblockchain network.

In some embodiments, each connection information package comprises afirst network address of a corresponding function permitted to use theconnection information package and a realm of the authenticationfunction. The first network address may be an IP address and a hostnameof the corresponding function. In certain embodiments, each connectioninformation package further comprises a public encryption key of thecorresponding function.

In some embodiments, at least one of the plurality of connectioninformation packages includes a validity parameter. In certainembodiments, at least one connection information package includes, asthe validity parameter, an expiration time and date of the correspondingconnection information package. Here, the corresponding connectioninformation package becoming invalid after the expiration time and date.In certain embodiments, at least one connection information packageincludes, as the validity parameter, an indicator of a permitted numberof authentication requests using the corresponding connectioninformation package. Here, the corresponding connection informationpackage becoming invalid after being used the permitted number of times.

The method 700 includes receiving 710, at the authentication functionand from a first function, a request to authenticate a user. In certainembodiments, receiving 710 the request to authenticate a user includesreceiving a user authentication request from a second IP addressbelonging the first function. In various embodiments, the first functionincludes an authentication, authorization, and accounting (“AAA”)function in a mobile communication network visited by the user.Moreover, the authentication function may include an AAA server in ahome network of the user.

In some embodiments, the request to authenticate a user comprises apackage identifier and a message authentication code. Here, the packageidentifier indicates a particular one of the plurality of connectioninformation packages and the message authentication code is computedbased on the private key of first function. The package identifier andmessage authentication code may be used to verify that the sender of therequest to authenticate a user is authorized to use the indicatedconnection information package.

The method 700 includes determining 715 whether the first function isassociated with a valid one of the plurality of connection informationpackages. Here, each connection information package may be associatedwith a specific entity permitted to use the connection informationpackage. In one embodiment, the sender of the message that triggered thecreation of the connection information package is the permitted entity.

In some embodiments, determining 715 whether the first function isassociated with a particular connection information package includeschecking whether the request to authenticate a user was received from anIP address or hostname included in the connection information package(e.g., whether the second network address matches the first networkaddress). Here, a hostname in the connection information package may beresolved into a first IP address which is then compared to the IPaddress of the first function (e.g., the second network address).Moreover, determining 715 whether the first function is associated witha connection information package may also include verifying the messageauthentication code using the public key of the particular connectioninformation package identified by the package identifier.

The method 700 includes accepting 720, at the authentication function,the request to authenticate a user in response to the first functionbeing associated with one of the plurality of connection informationpackage. In some embodiments, accepting 720 the authentication requestincludes authenticating the user via the first function. Moreover,accepting 720 the request in response to the first function beingassociated with a connection information package may also includerejecting the request to authenticate a user in response to determiningthat no connection information package is associated with to the firstfunction.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

1. An apparatus comprising: a transceiver that receives a request toauthenticate a user, the request containing a username and a realm; anda processor that: identifies a first address on a blockchain networkcorresponding to the realm; sends a message to the first address on theblockchain network, the message containing a payment; receive aconnection information package from the first address on the blockchainnetwork after the payment is confirmed; and establish a connection withan authentication server in the realm using the connection informationpackage; and authenticate the user via the authentication server in therealm.
 2. The apparatus of claim 1, wherein identifying the firstaddress on a blockchain network corresponding to the realm comprisesmapping the realm to an address on the blockchain network using apreconfigured table.
 3. The apparatus of claim 1, wherein identifyingthe first address on a blockchain network corresponding to the realmcomprises sending a domain name system (“DNS”) request, the requestincluding the realm, and receiving a DNS response, the DNS responseincluding the first address on the blockchain network.
 4. The apparatusof claim 1, wherein the first address on a blockchain network is theaddress of a smart contract on the blockchain network, the blockchainnetwork containing a single ledger shared among all nodes of theblockchain network, wherein the smart contract comprises executable codestored in the shared ledger of the blockchain network.
 5. The apparatusof claim 1, wherein the message sent to the first address on theblockchain network comprises a first network address of the apparatus,the first network address indicating one of an IP address and a hostnameof the apparatus, wherein the connection information package isassociated with the realm, and wherein the connection informationpackage includes the first network address of the apparatus.
 6. Theapparatus of claim 5, wherein the connection with the authenticationserver in the realm is made using the first network address, wherein themessage sent to the first address on the blockchain network furtherincludes a public key of the apparatus, and wherein the connectioninformation package includes the public key of the apparatus.
 7. Theapparatus of claim 6, wherein establishing the connection with theauthentication server in the realm using the connection informationpackage comprises sending a request message to the authenticationserver, the request message comprising a reference to the connectioninformation package and a message authentication code computed with aprivate key associated with the public key of the apparatus.
 8. Theapparatus of claim 1, wherein the connection information packageincludes a validity parameter that comprises an expiration time and dateof the connection information package, wherein the connectioninformation package becomes invalid after the expiration time and date.9. The apparatus of claim 1, wherein the connection information packageincludes a validity parameter that comprises an indicator of a permittednumber of authentication requests using the connection informationpackage, wherein the connection information package becomes invalidafter being used the permitted number of times.
 10. The apparatus ofclaim 1, wherein the connection information package includes contactinformation selected from the group consisting of: an IP address of theauthentication server in the realm, a hostname of the authenticationserver in the realm, a protocol to be used to contact the authenticationserver in the realm, and a port to be used to connect to theauthentication server in the realm.
 11. The apparatus of claim 1,wherein the blockchain network contains a single ledger shared among allnodes of the blockchain network, wherein the payment contained in themessage is a blockchain payment from a second address on the blockchainnetwork to the first address on the blockchain network, the secondaddress on the blockchain network belonging to an operator of theapparatus, and wherein receiving the connection information package fromthe first address on the blockchain network after the payment isconfirmed comprises receiving the connection information package inresponse to the payment being inserted into the shared ledger of theblockchain network.
 12. A method comprising: receiving, at a firstfunction, a request to authenticate a user, the request containing ausername and a realm; identifying a first address on a blockchainnetwork corresponding to the realm; sending a message to the firstaddress on the blockchain network, the message containing a payment;receiving a connection information package from the first address on theblockchain network after the payment is confirmed; establishing aconnection with an authentication server in the realm using theconnection information package; and authenticating the user via theauthentication server in the realm.
 13. The method of claim 12, whereinidentifying the first address on a blockchain network corresponding tothe realm comprises one of: mapping the realm to an address using apreconfigured table and sending a domain name system (“DNS”) request,the request including the realm, and receiving a DNS response, the DNSresponse including the first address on the blockchain network. 14.(canceled)
 15. (canceled)
 16. (canceled)
 17. (canceled)
 18. (canceled)19. (canceled)
 20. (canceled)
 21. (canceled)
 22. (canceled) 23.(canceled)
 24. (canceled)
 25. (canceled)
 26. The method of claim 12,wherein the first address on a blockchain network is the address of asmart contract on the blockchain network, the blockchain networkcontaining a single ledger shared among all nodes of the blockchainnetwork, wherein the smart contract comprises executable code stored inthe shared ledger of the blockchain network.
 27. The method of claim 12,wherein the message sent to the first address on the blockchain networkcomprises a first network address of the first function, the firstnetwork address indicating one of: an IP address and a hostname of thefirst function, wherein the connection information package is associatedwith the realm, and wherein the connection information package includesthe first network address of the first function.
 28. The method of claim27, wherein the connection with the authentication server in the realmis made using the first network address, wherein the message sent to thefirst address on the blockchain network further includes a public key ofthe first function, and wherein the connection information packageincludes the public key of the first function.
 29. The method of claim12, wherein the connection information package includes a validityparameter that comprises an expiration time and date of the connectioninformation package, wherein the connection information package becomesinvalid after the expiration time and date.
 30. The method of claim 12,wherein the connection information package includes a validity parameterthat comprises an indicator of a permitted number of authenticationrequests using the connection information package, wherein theconnection information package becomes invalid after being used thepermitted number of times.
 31. The method of claim 12, wherein theconnection information package includes contact information selectedfrom the group consisting of: an IP address of the authentication serverin the realm, a hostname of the authentication server in the realm, aprotocol to be used to contact the authentication server in the realm,and a port to be used to connect to the authentication server in therealm.
 32. The method of claim 12, wherein the blockchain networkcontains a single ledger shared among all nodes of the blockchainnetwork, wherein the payment contained in the message is a blockchainpayment from a second address on the blockchain network to the firstaddress on the blockchain network, the second address on the blockchainnetwork belonging to an operator of the first function, and whereinreceiving the connection information package from the first address onthe blockchain network after the payment is confirmed comprisesreceiving the connection information package in response to the paymentbeing inserted into the shared ledger of the blockchain network.